Remote Configuration of Nodinite Monitoring Agent for DataPower
This guide provides instructions for configuring the Nodinite DataPower Monitoring Agent.
Remote Configuration is unavailable if the [Monitoring Agent Configuration][] is not authenticated or is using Microsoft Service Bus Relaying.
The following steps must first be performed and are required for the usage of the Remote Configuration of the agent:
- Establish communication between the Monitoring Service and the Monitoring
using:
1.1 TCP/IP (HTTP)
1.2 Service Bus Relaying - Configure the Monitoring Agent Configuration
To use this agent from Nodinite, a Monitoring Agent Configuration must exist that points to this agent.
2.1. A Monitoring Agents must be defined within the Web Client
IM: http://SERVER/IM/WebClient/Admin/Sources
YouTube: https://www.youtube.com/watch?v=-ky8QqyQAHE
2.2 Name the Monitoring Agent Configuration (mandatory)
2.3 Give the Monitoring Agent Configuration a short description (optional)
2.4 Enter the Service URI using the information from 1.1 or 1.2 (mandatory)Note
This URI might need to be changed to localhost/proper DNS/Alias name depending on infrastructure 2.5 Enter a polling interval for this Monitoring Agent Configuration. A short poll interval might affect performance, tune this setting according to your needs and resources.
2.6 Enter the Authentication Key using the information from file README.txt -- Authentication Key: THEKEY
2.7 Save
Use Remote Configuration to configure the agent
Create Monitor Views that use the Monitoring Agents or selected Resources according to business demands.
Communication Options
1.1 TCP/IP (HTTP)
1.2 Service Bus Relaying
You must enable Service Bus Relaying if the Agent is running off-site or in the cloud without the ability to communicate directly using TCP/IP.
2. Add a Monitoring Agent Configuration
After the successful installation, you must add a Monitoring Agent in the Web Client to access the Remote Configuration for the installed agent.
Remote Configuration of DataPower Servers
The Remote Configuration for the Nodinite DataPower Monitoring Agent provides the ability to configure the agent remotely, even if the agent is installed off-site.
Configurations on the Resource can be adjusted via the Action button if the Monitor View has the Remote Actions feature enabled.
Protocols The following protocols are supported by the agent:
- SNMP
Settings
There are some general settings for the agent available in the Settings tab.
Environment
Part of the standard features shared with all Monitoring Agents is an option to set the name of the target environment, for example, TEST, QA, PROD.
Debug
Part of the common features shared with all Monitoring Agents, there is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. The Default is unchecked.
Culture Information
The Culture Information setting determines how the Web Client displays the date and time for file Resources in Monitor Views.
About SNMP
To test the settings you could use an external tool like SnmpB You find the SNMP V3 EngineId in DataPower
NOTICE that you should remove the 0x and only use like 8000395d030242ac110002 when enter the settings in remote config.
Datapower
Any number of DataPower instances can be monitored, add by clicking the Add button in the 'Data Power SNMP' tab.
![DataPower tab][]
Expand the Accordion to edit content.
- Connection
- Disk
- CPU
- Memory
- Services
- Notification Rules
Connection
The Connection tab lets you configure SNMP-related settings needed to fetch SNMP and SNMP Trap events from your DataPower instance.
- Display Name
- SNMP Trap Port
- Server
- Port
- SNMP Version
- Security Name
- Security Level
- Context Name
- Context Engine ID
Display Name The user-friendly name for Resource.
SNMP Trap Port Local port on site for the Monitoring Agent to receive SNMP traps on, default port is 162.
Server The IP address of your DataPower instance to monitor
Port Port to use when communicating directly with DataPower instance, default 161
SNMP Version
Select the version to use when the agent connects to your DataPower instance. Default V3
Security Name
Context Name
Context Engine ID
Disk
Save
You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.
Here's an example of the Save options.
Note
Depending on the synchronization interval set for the agent, there might be a delay before the Web Client reflects upon the change. You can force the agent to synchronize the [Configuration][] for all Nodinite Monitoring Agents.
Save and close, save, and close the dialogue.
Cancel, closes the dialogue without saving any changes.
Next Step
Install DataPower Monitoring Agent
Related
[DataPower][]
Monitor Views
Monitoring Agents